Rewrite Notifications #295
Conversation
|
|
…umentation into rewrite/notifications
# Conflicts: # firebase.json
|
|
||
| # Notifications | ||
|
|
||
| **Mobile Notifications** are alerts or messages that appear on a user's device outside the normal UI flow of an app. They can inform the user of time-sensitive or high-priority messages, events, or actions that require attention. Notifications may appear as banners, alerts, pop-ups, or lock-screen notifications, depending on user preferences and platform design guidelines. |
There was a problem hiding this comment.
Why are we just calling it mobile? There can be web notifications as well right?
There was a problem hiding this comment.
Yes, removed 'mobile' from multiple places.
|
|
||
| Generally, mobile notifications can be divided into two main categories: **Local Notifications** and **Push (remote) Notifications**. | ||
|
|
||
| **Local Notifications** are scheduled directly on the device and do not require a server component. They are commonly used for time-based reminders or location-based triggers, such as a daily workout reminder at 7:00 AM. To implement local notifications in FlutterFlow, you can integrate the [flutter_local_notifications](https://pub.dev/packages/flutter_local_notifications) package using custom actions. |
There was a problem hiding this comment.
Add a link to custom actions page
| Before you begin, ensure that you have: | ||
| - Completed all steps in the | ||
| [**Firebase Setup**](../../ff-integrations/firebase/connect-to-firebase-setup.md). | ||
| - Upgraded your Firebase project to the [**Blaze plan**](https://firebase.google.com/pricing) to enable cloud functions required for push notifications. |
There was a problem hiding this comment.
it would be good to mention that cloud funcs are only required for flutterflow setup for push notifs such as getting fcm token & sending push notifications trigger from flutterflow.
| 3. Optionally, you can enable **Allow Scheduling** to send push notifications at a later time. Once enabled, you can select **Scheduler Granularity**, which determines how precisely the notifications will be sent. You can choose the granularity based on how time-sensitive your notifications are; For example: | ||
| - If you need the notification to be sent at an **exact time** (e.g., 11:37 AM), choose **"1 minute"**. | ||
| - If a slight delay is acceptable, you can select **"15 minutes"** or **"1 hour"**, meaning the notification will be sent within that timeframe. | ||
| - **Higher precision (e.g., 1-minute intervals) requires more computing resources**, which may **slightly increase costs** (up to $0.50 per month). |
There was a problem hiding this comment.
Great job of including the pricing info!
|
|
||
|
|
||
|
|
||
| :::tip |
There was a problem hiding this comment.
| :::tip | |
| :::warning[Upgrading to Blaze Plan] |
| allow="clipboard-write"> | ||
| </iframe> | ||
| </div> | ||
| <p></p> |
There was a problem hiding this comment.
Add a note that this key is allowed to download only once.
There was a problem hiding this comment.
Added! updated directly in Arcade.
| Each device is identified by a unique **Device Token/Registration Token** generated by the FCM to target specific devices. The Mobile App on the user's device receives these notifications and handles the payload by displaying messages or navigating the user to specific screens. | ||
|
|
||
|
|
||
| ## Add Push Notifications |
There was a problem hiding this comment.
| ## Add Push Notifications | |
| ## Push Notifications Setup |
| </div> | ||
| <p></p> | ||
|
|
||
| ### Send Push Notifications |
There was a problem hiding this comment.
| ### Send Push Notifications | |
| ## Send Push Notifications |
| - **Deliver With Sound** **(Optional):** Enable this option if you want the notification to play a sound. | ||
| - **Batch Notifications** **(Optional):** Toggle this setting if you want to send the notification in batches. Enable this only when you have over 10K users. | ||
| - **Scheduled Time (Optional):** Choose the specific date and time for the notification to be sent. This option is available only when the **Allow Scheduling** option is enabled, and the selected date and time follow your timezone. | ||
| - **User References (Optional):** Send push notifications to a specific user or a few users. Enter the user document reference (from the 'users' collection in Firestore) into the *User References*. |
There was a problem hiding this comment.
maybe a small example because i think the format is users/userId instead of just userId
There was a problem hiding this comment.
Added the format and image to ensure there’s no room for confusion.
|
|
||
| :::tip | ||
|
|
||
| On the page that receives the DocumentReference, you can fetch additional details of the item using the [**Backend Query**](#). |
There was a problem hiding this comment.
# goes nowhere.
Also maybe this is a good example to add? Like what to do when the notification data is received? We can create a separate ticket for this and add the example later maybe?
There was a problem hiding this comment.
Updated the '#' and yes we can add that example in a new ticket.
No problem :) All review comments are addressed now. Merging it... |
Description
Rewrite Notifications
Linear ticket and magic word Fixes DEVR-368
Type of change